-
Notifications
You must be signed in to change notification settings - Fork 0
📝 Add Board Affiliation and Co-Affiliation limits (4.9 and 4.10) #5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
(a) is an employee, officer, or member of the Board of Directors of another entity; | ||
|
||
(b) maintains a significant consulting relationship with another entity; or | ||
|
||
(c) owns at least 1% of the equity or debt, or derivatives thereof, of another entity. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(a) is an employee, officer, or member of the Board of Directors of another entity; | |
(b) maintains a significant consulting relationship with another entity; or | |
(c) owns at least 1% of the equity or debt, or derivatives thereof, of another entity. | |
1. is an employee, officer, or member of the Board of Directors of another entity | |
2. maintains a significant consulting relationship with another entity; or | |
3. owns at least 1% of the equity or debt, or derivatives thereof, of another entity. |
Is it possible for us to use more accessible formatting for this as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is fine to do, but I'm going to leave it open, in case there's a legal(ease) reason that I'm not aware of for why we should keep it.
(noting this mostly to myself, but we should probably preview it in case we need to indent the bullets since our overall doc structure is weird to being with)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should do this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to close this because it breaks the format we have with sub-sections (maybe sub-sub-sections) and it looks weird.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not going to die on this hill but I don’t understand your points Jeff so I’d like to revisit this? Creating lists in content without using semantic lists markup is an accessibility own goal. I don’t think it would prevent anyone from understanding the content but it’s probably something I would fail an accessibility audit for if I was auditing (WCAG SC 1.3.1 Info and Relationships
Co-authored-by: Thibaud Colas <thibaudcolas@gmail.com>
Co-authored-by: Thibaud Colas <thibaudcolas@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏻
This looks all good to me if we can resolve the remaining open comments. |
This just passed by the board. |
Fixes #4
For any members who are interested in the Forum thread: https://forum.djangoproject.com/t/dsf-bylaws-are-now-on-github/40262